This PR adds a functionality or fixes a bug.
OR
This PR marks a new Gens release. We apply semantic versioning. This is a major/minor/patch release for reasons.

How to test:

1. how to test it, possibly with real cases/data

Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.

Review:

• code approved by

Discussion points

• How to deal with the .github workflows set up by Stockholm? (Working with their instance)
• Addition of case_id. What consequences? I suspect we will need to migrate our Gens db before merge.
• Updates to preprocessing scripts generate_gens_data.pl and gvcfvaf.pl. Needs to be tested separately? We are using a different script in the ol' wgs repo?
• Individual ID used in addition to the sample_id and case_id. What is the significance?
• Leaving out for now as it is not completed: Start something that would Fix #32 Clinical-Genomics/gens#92
• The changelog is a mess. Let's see how to organize it.
• Looks like Gens is merging with Scout through its database. Let's think about how we want to approach that.

Migration steps

• Update the case_id. Here for a single test sample: db.samples.updateOne({}, {"$set": {"case_id": "hg002"}})
• Login screen. Make sure it works OK. Seems to look for user email in the Scout db, which should work good enough for now. Do we want to use the same LDAP system as in Scout eventually?